Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdb8777d14a4462b1aabf7e8c72d890def39fc0db8c44b10ac7c8632ae3a3916

Tx prefix hash: 203437280d4f276032852dd3d752af62f7bfc21288e6631220d3f0d689fb85c5
Tx public key: 7e5168e52ca8e2e3a4991ef7f59160d8d24d25fadfd61c8feb62cef389dc1398
Timestamp: 1700116246 Timestamp [UCT]: 2023-11-16 06:30:46 Age [y:d:h:m:s]: 02:079:07:57:52
Block: 892705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 576405 RingCT/type: yes/0
Extra: 017e5168e52ca8e2e3a4991ef7f59160d8d24d25fadfd61c8feb62cef389dc139802110000000ee6d27f9c000000000000000000

1 output(s) for total of 0.676235163000 dcy

stealth address amount amount idx
00: 774fe9bb9b20da4eae11cf7f31a59a6e3bca56208100b84efe2f3f1d9565830b 0.676235163000 1348828 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": 892715, "vin": [ { "gen": { "height": 892705 } } ], "vout": [ { "amount": 676235163, "target": { "key": "774fe9bb9b20da4eae11cf7f31a59a6e3bca56208100b84efe2f3f1d9565830b" } } ], "extra": [ 1, 126, 81, 104, 229, 44, 168, 226, 227, 164, 153, 30, 247, 245, 145, 96, 216, 210, 77, 37, 250, 223, 214, 28, 143, 235, 98, 206, 243, 137, 220, 19, 152, 2, 17, 0, 0, 0, 14, 230, 210, 127, 156, 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