Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 366b79e374753e842c1ae819dcb3e3bd9b4798088f9c4c4d9f73d765cc98c602

Tx prefix hash: da7ab07f913e9f74b0c385a427e514790df6c9da42fea2d0ff4d601c8f49de2f
Tx public key: c4b4615e0aaa1499d175d4bea6bef8e8e656a7724b63f84723ed2f9d7f561b01
Timestamp: 1736138687 Timestamp [UCT]: 2025-01-06 04:44:47 Age [y:d:h:m:s]: 00:162:01:17:29
Block: 1191224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115532 RingCT/type: yes/0
Extra: 01c4b4615e0aaa1499d175d4bea6bef8e8e656a7724b63f84723ed2f9d7f561b0102110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: caa1bf30608936ab346eaf43d62649574c6286b620c24c281c40f88d4156b8fe 0.600000000000 1677747 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": 1191234, "vin": [ { "gen": { "height": 1191224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caa1bf30608936ab346eaf43d62649574c6286b620c24c281c40f88d4156b8fe" } } ], "extra": [ 1, 196, 180, 97, 94, 10, 170, 20, 153, 209, 117, 212, 190, 166, 190, 248, 232, 230, 86, 167, 114, 75, 99, 248, 71, 35, 237, 47, 157, 127, 86, 27, 1, 2, 17, 0, 0, 0, 11, 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