Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c1fbc0c3b232b95e8923dc43359bce9ec468e2686561e8e504c699120b9d26c

Tx prefix hash: 005b8a8e582cf41da1f7fdcae20fe89bd84c9f2c57c87627ba2039ca85ae9773
Tx public key: 683ef46afc32c2503ee4d033785de800a0f1a3b76ab080f355b0b9ac504f1bbf
Timestamp: 1724621775 Timestamp [UCT]: 2024-08-25 21:36:15 Age [y:d:h:m:s]: 00:234:08:02:04
Block: 1095869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167340 RingCT/type: yes/0
Extra: 01683ef46afc32c2503ee4d033785de800a0f1a3b76ab080f355b0b9ac504f1bbf02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bebc33677d99590a37535ac25b61b1b5699e8c323af53cbb1eca441cdaad44c 0.600000000000 1571052 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": 1095879, "vin": [ { "gen": { "height": 1095869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bebc33677d99590a37535ac25b61b1b5699e8c323af53cbb1eca441cdaad44c" } } ], "extra": [ 1, 104, 62, 244, 106, 252, 50, 194, 80, 62, 228, 208, 51, 120, 93, 232, 0, 160, 241, 163, 183, 106, 176, 128, 243, 85, 176, 185, 172, 80, 79, 27, 191, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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