Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88f43b8d9ab2ab8c5922bf6da37f742543576d51429f4bd56f1eaf32bad3df96

Tx prefix hash: 4d8b750e59b4ee24fd1cc9bf496a0553482ad702e1f3e9d3d7796cefd36ba3c6
Tx public key: 6865b4f6542084919491047312e2ba012a1aef05c5b1537f027b97f5ae8ae2ba
Timestamp: 1737553405 Timestamp [UCT]: 2025-01-22 13:43:25 Age [y:d:h:m:s]: 00:334:07:03:49
Block: 1202892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236505 RingCT/type: yes/0
Extra: 016865b4f6542084919491047312e2ba012a1aef05c5b1537f027b97f5ae8ae2ba021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: adf6d2732e477a55f02f5a1c915dbcce8adf76256422ab28cd716f7386986b1e 0.600000000000 1689559 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": 1202902, "vin": [ { "gen": { "height": 1202892 } } ], "vout": [ { "amount": 600000000, "target": { "key": "adf6d2732e477a55f02f5a1c915dbcce8adf76256422ab28cd716f7386986b1e" } } ], "extra": [ 1, 104, 101, 180, 246, 84, 32, 132, 145, 148, 145, 4, 115, 18, 226, 186, 1, 42, 26, 239, 5, 197, 177, 83, 127, 2, 123, 151, 245, 174, 138, 226, 186, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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