Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e4a45fd84848a55d844a885daedaef3527e8576e36c9dca4f56d56d59a2e1d9

Tx prefix hash: cc9dc3bf264de8e862367f81f976937e66677dafd83505520b651049cfca8863
Tx public key: b78f9e25a4d3193d389d28a38d4657640c4853118cac153d04f9d22aee8addfe
Timestamp: 1710486589 Timestamp [UCT]: 2024-03-15 07:09:49 Age [y:d:h:m:s]: 01:250:05:07:17
Block: 978705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437520 RingCT/type: yes/0
Extra: 01b78f9e25a4d3193d389d28a38d4657640c4853118cac153d04f9d22aee8addfe021100000001a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2064a5e4a7b6330ff663bbccc0db95e4f6052de3b815b1ff5c21846ba3247db0 0.600000000000 1438734 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": 978715, "vin": [ { "gen": { "height": 978705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2064a5e4a7b6330ff663bbccc0db95e4f6052de3b815b1ff5c21846ba3247db0" } } ], "extra": [ 1, 183, 143, 158, 37, 164, 211, 25, 61, 56, 157, 40, 163, 141, 70, 87, 100, 12, 72, 83, 17, 140, 172, 21, 61, 4, 249, 210, 42, 238, 138, 221, 254, 2, 17, 0, 0, 0, 1, 165, 223, 157, 134, 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