Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7365e1fcc542938b23041d183c0c0a65230f3679280da2455e6ab8a9f4aebb4f

Tx prefix hash: dd73b7fa04fb2f5e44f0752f67ac3cc0bda536c8156131a1ce8d04b618711c2e
Tx public key: a249e77a7aff2dcdac8eb384319839013b30b1ca5f009eee30de6c7bd570000a
Timestamp: 1740996941 Timestamp [UCT]: 2025-03-03 10:15:41 Age [y:d:h:m:s]: 00:255:21:24:02
Block: 1231167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180642 RingCT/type: yes/0
Extra: 01a249e77a7aff2dcdac8eb384319839013b30b1ca5f009eee30de6c7bd570000a02110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d60b0368b6c4cec615fd971f475ced14b92236fd58a8ddcfed6f69b822b7833a 0.600000000000 1718072 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": 1231177, "vin": [ { "gen": { "height": 1231167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d60b0368b6c4cec615fd971f475ced14b92236fd58a8ddcfed6f69b822b7833a" } } ], "extra": [ 1, 162, 73, 231, 122, 122, 255, 45, 205, 172, 142, 179, 132, 49, 152, 57, 1, 59, 48, 177, 202, 95, 0, 158, 238, 48, 222, 108, 123, 213, 112, 0, 10, 2, 17, 0, 0, 0, 12, 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