Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1d575820e3d09a2959c87f41ce22fbfcf400a8abf52df51b80f851cecbf37a8

Tx prefix hash: 03de44da3a0829bcd293f4937d93af9a273bf9fd12a423e8ee7847f1a09bed6d
Tx public key: f8513ca097bfdbc88888369fa3c156632a2c51b3b5d603ba493e67515df5cfd3
Timestamp: 1712907550 Timestamp [UCT]: 2024-04-12 07:39:10 Age [y:d:h:m:s]: 01:201:23:51:21
Block: 998738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403045 RingCT/type: yes/0
Extra: 01f8513ca097bfdbc88888369fa3c156632a2c51b3b5d603ba493e67515df5cfd302110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38d9d12e65c093af7761aae307bc686b50bb405b76ef28746b43d07fd63a924b 0.600000000000 1459190 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": 998748, "vin": [ { "gen": { "height": 998738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38d9d12e65c093af7761aae307bc686b50bb405b76ef28746b43d07fd63a924b" } } ], "extra": [ 1, 248, 81, 60, 160, 151, 191, 219, 200, 136, 136, 54, 159, 163, 193, 86, 99, 42, 44, 81, 179, 181, 214, 3, 186, 73, 62, 103, 81, 93, 245, 207, 211, 2, 17, 0, 0, 0, 6, 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