Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3cfd0428a0f9215bb147e16b65fca9a29a7cb557de8cffbc1f33594a1db93de

Tx prefix hash: 3795a5ca3888ea31974b1837dd2505912538a5ccaa6dd00ee1a9457223fa5d72
Tx public key: d682b28f48291b15a5ebf1b45b11a9904ad4b104525b2e54fa841afc6d1ea2bc
Timestamp: 1738456228 Timestamp [UCT]: 2025-02-02 00:30:28 Age [y:d:h:m:s]: 00:248:07:15:51
Block: 1210133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175170 RingCT/type: yes/0
Extra: 01d682b28f48291b15a5ebf1b45b11a9904ad4b104525b2e54fa841afc6d1ea2bc021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e63f2c069999a06da04deca8d97ead0350976957a206593d90d56e4a989ecc2 0.600000000000 1696884 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": 1210143, "vin": [ { "gen": { "height": 1210133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e63f2c069999a06da04deca8d97ead0350976957a206593d90d56e4a989ecc2" } } ], "extra": [ 1, 214, 130, 178, 143, 72, 41, 27, 21, 165, 235, 241, 180, 91, 17, 169, 144, 74, 212, 177, 4, 82, 91, 46, 84, 250, 132, 26, 252, 109, 30, 162, 188, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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