Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 496f6576c0431fb96fcfe3f86e0a0e716c7aad9648a1a5367d601c04e8417ba2

Tx prefix hash: f372fd0f25c4d130c05e5ecc8533c9e8e7f2f9e4a02e506dcdadd5814b5ea8af
Tx public key: 96eb8c05ed52597def33cf234ad35afb5cc60c1323572b0e5a9a46e3a1f8e578
Timestamp: 1715942919 Timestamp [UCT]: 2024-05-17 10:48:39 Age [y:d:h:m:s]: 01:028:05:59:50
Block: 1023927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281038 RingCT/type: yes/0
Extra: 0196eb8c05ed52597def33cf234ad35afb5cc60c1323572b0e5a9a46e3a1f8e57802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ed4bd08b90ceb1fbeb7d03b4f6988aed355461e4d924404b10d034dac870fdc 0.600000000000 1489270 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": 1023937, "vin": [ { "gen": { "height": 1023927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ed4bd08b90ceb1fbeb7d03b4f6988aed355461e4d924404b10d034dac870fdc" } } ], "extra": [ 1, 150, 235, 140, 5, 237, 82, 89, 125, 239, 51, 207, 35, 74, 211, 90, 251, 92, 198, 12, 19, 35, 87, 43, 14, 90, 154, 70, 227, 161, 248, 229, 120, 2, 17, 0, 0, 0, 5, 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