Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73d4f977216c39e142acd4e150f4af6249a4c15620de41b0e6bb6ba900101332

Tx prefix hash: 4d7b1c7a59420b74d92df3297bd42279c981415743afc0b71b5ff4e76c1852f5
Tx public key: 6d4b39392fdbb2bdcaaf9d131e8b91b855f74e407a906a633c7814c48a65c246
Timestamp: 1702132889 Timestamp [UCT]: 2023-12-09 14:41:29 Age [y:d:h:m:s]: 01:188:16:35:38
Block: 909428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395956 RingCT/type: yes/0
Extra: 016d4b39392fdbb2bdcaaf9d131e8b91b855f74e407a906a633c7814c48a65c24602110000000c4b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82b967ba230c8944a8d4ce34f2bc10b342e7c791926a3f73836537c222e8a29c 0.600000000000 1366515 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": 909438, "vin": [ { "gen": { "height": 909428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82b967ba230c8944a8d4ce34f2bc10b342e7c791926a3f73836537c222e8a29c" } } ], "extra": [ 1, 109, 75, 57, 57, 47, 219, 178, 189, 202, 175, 157, 19, 30, 139, 145, 184, 85, 247, 78, 64, 122, 144, 106, 99, 60, 120, 20, 196, 138, 101, 194, 70, 2, 17, 0, 0, 0, 12, 75, 143, 81, 34, 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