Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cc3f4830c56fb4819547ecf5d4a0e6ea66ef77eb85e6936d86955acce29a975

Tx prefix hash: 05f5f30b05de3c5874db3b13ebbbe2a85cec1f7b0328100a4e294df5453ca3b3
Tx public key: 14a9208163d451baa2baf937890ac716fdcf4a714d1838ca2871a6ce76f1cb5e
Timestamp: 1761014419 Timestamp [UCT]: 2025-10-21 02:40:19 Age [y:d:h:m:s]: 00:079:11:25:28
Block: 1394482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56897 RingCT/type: yes/0
Extra: 0114a9208163d451baa2baf937890ac716fdcf4a714d1838ca2871a6ce76f1cb5e02110000000501491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cfa3ba84fd42d2064a6638be91f9a56cab4d95236659827898fa4535d3e5771 0.600000000000 1882753 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": 1394492, "vin": [ { "gen": { "height": 1394482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cfa3ba84fd42d2064a6638be91f9a56cab4d95236659827898fa4535d3e5771" } } ], "extra": [ 1, 20, 169, 32, 129, 99, 212, 81, 186, 162, 186, 249, 55, 137, 10, 199, 22, 253, 207, 74, 113, 77, 24, 56, 202, 40, 113, 166, 206, 118, 241, 203, 94, 2, 17, 0, 0, 0, 5, 1, 73, 31, 136, 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