Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a884e775807f9f3224bb054b023485d485a90c4bdc6e1aeff7cbd12474249e0d

Tx prefix hash: ca7c943dcbdc886e5b98cd974a28bd9df2ef4440ca1b1b565c046e7ccc7ad43f
Tx public key: 5819a077679edde79de4c6956954afc3926914e6b5a54f4279c50db1aaca5d1c
Timestamp: 1632089480 Timestamp [UCT]: 2021-09-19 22:11:20 Age [y:d:h:m:s]: 03:104:18:33:18
Block: 337121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 850876 RingCT/type: yes/0
Extra: 015819a077679edde79de4c6956954afc3926914e6b5a54f4279c50db1aaca5d1c02110000001e5410958b000000000000000000

1 output(s) for total of 46.879030097000 dcy

stealth address amount amount idx
00: c555bccc12dc5dbf3467efc0f874d572256eed74cc9222b62b502f1f676187e5 46.879030097000 694298 of 0

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": 337131, "vin": [ { "gen": { "height": 337121 } } ], "vout": [ { "amount": 46879030097, "target": { "key": "c555bccc12dc5dbf3467efc0f874d572256eed74cc9222b62b502f1f676187e5" } } ], "extra": [ 1, 88, 25, 160, 119, 103, 158, 221, 231, 157, 228, 198, 149, 105, 84, 175, 195, 146, 105, 20, 230, 181, 165, 79, 66, 121, 197, 13, 177, 170, 202, 93, 28, 2, 17, 0, 0, 0, 30, 84, 16, 149, 139, 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