Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1d2dc533f0f0f16b56d26e33d8633d7d981de792f98b53a2c36102b12757413

Tx prefix hash: e83c3f42272b7b1b2333260b701cf7efbe46ab887e234bd738fb8145220e51fa
Tx public key: 500dcbe3e63a0c5af84cfe3299fb110e06a2a66b48eb0f3bb1d013e9b158707b
Timestamp: 1736696668 Timestamp [UCT]: 2025-01-12 15:44:28 Age [y:d:h:m:s]: 00:158:09:12:47
Block: 1195838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112878 RingCT/type: yes/0
Extra: 01500dcbe3e63a0c5af84cfe3299fb110e06a2a66b48eb0f3bb1d013e9b158707b0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2232209bc834184c3dd5a3bfcfd33571d2736c62b473c83859540bbfe364b686 0.600000000000 1682431 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": 1195848, "vin": [ { "gen": { "height": 1195838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2232209bc834184c3dd5a3bfcfd33571d2736c62b473c83859540bbfe364b686" } } ], "extra": [ 1, 80, 13, 203, 227, 230, 58, 12, 90, 248, 76, 254, 50, 153, 251, 17, 14, 6, 162, 166, 107, 72, 235, 15, 59, 177, 208, 19, 233, 177, 88, 112, 123, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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