Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a5e31bf647d106d1debf34dbc7a8d43c764de78a678cd1d4f4c8dd7566e780b

Tx prefix hash: 3741107b0282c725910198a2423bfd4fa33e2b2ae3f9056c866a33dc79c3d999
Tx public key: dd582202d089fa3cce85e85d8249f2aa68fff319af48efab7fe06d0542b66d07
Timestamp: 1721151988 Timestamp [UCT]: 2024-07-16 17:46:28 Age [y:d:h:m:s]: 00:286:21:20:42
Block: 1067124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204974 RingCT/type: yes/0
Extra: 01dd582202d089fa3cce85e85d8249f2aa68fff319af48efab7fe06d0542b66d070211000000015ff1157f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c3a81c61319bde93a3c5fb33e33a0b21008d5848a6f4dbc6079a57c47eddae2 0.600000000000 1537851 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": 1067134, "vin": [ { "gen": { "height": 1067124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c3a81c61319bde93a3c5fb33e33a0b21008d5848a6f4dbc6079a57c47eddae2" } } ], "extra": [ 1, 221, 88, 34, 2, 208, 137, 250, 60, 206, 133, 232, 93, 130, 73, 242, 170, 104, 255, 243, 25, 175, 72, 239, 171, 127, 224, 109, 5, 66, 182, 109, 7, 2, 17, 0, 0, 0, 1, 95, 241, 21, 127, 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