Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 962c9b385375c82d6ca8cf1488831b6b2d41fdca9dbd9daed518ae703f2f6142

Tx prefix hash: ec7bb4e3be4093b0808987cc2a2ec6b8833864a6d894078e7ffc3907b90fea49
Tx public key: 605a46545e6c067488543779efe90c877f63fda8f128f21b248d3ed2cb8d7f78
Timestamp: 1740315572 Timestamp [UCT]: 2025-02-23 12:59:32 Age [y:d:h:m:s]: 00:227:06:58:57
Block: 1225509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160156 RingCT/type: yes/0
Extra: 01605a46545e6c067488543779efe90c877f63fda8f128f21b248d3ed2cb8d7f7802110000000625a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60a5fd47ed21860f000b708c2e82c545711397b6b5b41a73304e4bc88cb00d3a 0.600000000000 1712374 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": 1225519, "vin": [ { "gen": { "height": 1225509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60a5fd47ed21860f000b708c2e82c545711397b6b5b41a73304e4bc88cb00d3a" } } ], "extra": [ 1, 96, 90, 70, 84, 94, 108, 6, 116, 136, 84, 55, 121, 239, 233, 12, 135, 127, 99, 253, 168, 241, 40, 242, 27, 36, 141, 62, 210, 203, 141, 127, 120, 2, 17, 0, 0, 0, 6, 37, 163, 90, 15, 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