Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 372e4188c99eb831ef6e45428b93d9a7376b78f2f9cef3892c87f7c4baa68229

Tx prefix hash: f4f2e0ccbec9e4c5914cd8da93e8b61e643b90d9d5884f1f3d7533ab681ad6d7
Tx public key: 5328999f749d275fc5ef2da0709348aac857730b341a9be0bd408b5ab3c44575
Timestamp: 1730232153 Timestamp [UCT]: 2024-10-29 20:02:33 Age [y:d:h:m:s]: 00:159:00:29:46
Block: 1142328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113454 RingCT/type: yes/0
Extra: 015328999f749d275fc5ef2da0709348aac857730b341a9be0bd408b5ab3c4457502110000000ba11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb9cfa1aee6a9ee4037660ffc99d82d1c196fad9029536e40f78b62d1003e7ae 0.600000000000 1626177 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": 1142338, "vin": [ { "gen": { "height": 1142328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb9cfa1aee6a9ee4037660ffc99d82d1c196fad9029536e40f78b62d1003e7ae" } } ], "extra": [ 1, 83, 40, 153, 159, 116, 157, 39, 95, 197, 239, 45, 160, 112, 147, 72, 170, 200, 87, 115, 11, 52, 26, 155, 224, 189, 64, 139, 90, 179, 196, 69, 117, 2, 17, 0, 0, 0, 11, 161, 29, 186, 152, 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