Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 915b6fdcb922f796fee34c1ebafab472d4f75f85f5bf83f74e5b98eb3ba483d7

Tx prefix hash: e6cbdbd083a1fae7b2aa3625958444dcec82df5db9983696704ed90a8070bb39
Tx public key: 22dde3bbd90ba0b75035b2d08189946b0f80874cbe2bb1e7e476521dd3869d1f
Timestamp: 1732017158 Timestamp [UCT]: 2024-11-19 11:52:38 Age [y:d:h:m:s]: 00:162:07:01:51
Block: 1157095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115810 RingCT/type: yes/0
Extra: 0122dde3bbd90ba0b75035b2d08189946b0f80874cbe2bb1e7e476521dd3869d1f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b4aaaa62ec162f3305c613499c4b9d6023f1559a28743f400045fa2ec22d1a3 0.600000000000 1642718 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": 1157105, "vin": [ { "gen": { "height": 1157095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b4aaaa62ec162f3305c613499c4b9d6023f1559a28743f400045fa2ec22d1a3" } } ], "extra": [ 1, 34, 221, 227, 187, 217, 11, 160, 183, 80, 53, 178, 208, 129, 137, 148, 107, 15, 128, 135, 76, 190, 43, 177, 231, 228, 118, 82, 29, 211, 134, 157, 31, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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