Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d53068a823aeac92f48d314cba41b0ea7b9b86fbda3cb3fced386b50999d75f

Tx prefix hash: 52b42d768e9ecf1fdb49fa236ddb4f8ef28dfa619611d82ce1a3652293676b1c
Tx public key: ed5d0b3716ecebc9f96f441317b5808743951397a510779ea2cdbc1840b1f1eb
Timestamp: 1711503273 Timestamp [UCT]: 2024-03-27 01:34:33 Age [y:d:h:m:s]: 01:050:21:57:12
Block: 987137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297356 RingCT/type: yes/0
Extra: 01ed5d0b3716ecebc9f96f441317b5808743951397a510779ea2cdbc1840b1f1eb02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3122cb34c06b133abd655c8900a962b7aa97a777babddf316a033d014f7153ca 0.600000000000 1447378 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": 987147, "vin": [ { "gen": { "height": 987137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3122cb34c06b133abd655c8900a962b7aa97a777babddf316a033d014f7153ca" } } ], "extra": [ 1, 237, 93, 11, 55, 22, 236, 235, 201, 249, 111, 68, 19, 23, 181, 128, 135, 67, 149, 19, 151, 165, 16, 119, 158, 162, 205, 188, 24, 64, 177, 241, 235, 2, 17, 0, 0, 0, 7, 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