Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4e5b977b090f72218aba9b066177618724534514708cfb726a013d1644e73db7

Tx prefix hash: 783dff85b45fe4b0cea78f6100f926945bde677caf5baf99b0e020b4f59c5d24
Tx public key: e1e8c77bef6d2bd1566679450baa71ed333bf2a941d4085a39f07ca4aa86c47d
Timestamp: 1707077773 Timestamp [UCT]: 2024-02-04 20:16:13 Age [y:d:h:m:s]: 01:023:23:35:46
Block: 950414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278169 RingCT/type: yes/0
Extra: 01e1e8c77bef6d2bd1566679450baa71ed333bf2a941d4085a39f07ca4aa86c47d02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee9952b549423aa3e7b0de3c748aaa7e1de2d705e61d4cf80091a4b5a31231dc 0.600000000000 1409032 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 950424, "vin": [ { "gen": { "height": 950414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee9952b549423aa3e7b0de3c748aaa7e1de2d705e61d4cf80091a4b5a31231dc" } } ], "extra": [ 1, 225, 232, 199, 123, 239, 109, 43, 209, 86, 102, 121, 69, 11, 170, 113, 237, 51, 59, 242, 169, 65, 212, 8, 90, 57, 240, 124, 164, 170, 134, 196, 125, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8