Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46964185faa2f8f8ccdfcd441409916dde1851c487420b577d6fb71b00c883c1

Tx prefix hash: 6de1f2b310d87d389d33314d41668bc145bde0a7e8881f37e07375c9bde46b97
Tx public key: a8c9b986c882e2465f12572a1eaa513d1383444ab2086fe7e603ba4ce545c895
Timestamp: 1735963781 Timestamp [UCT]: 2025-01-04 04:09:41 Age [y:d:h:m:s]: 00:303:07:33:22
Block: 1189774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214263 RingCT/type: yes/0
Extra: 01a8c9b986c882e2465f12572a1eaa513d1383444ab2086fe7e603ba4ce545c89502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 706962d1c5de4dc15b05f7ec2ba16c1a5735e2645a60c6b90dd377eaec6b6e5c 0.600000000000 1676285 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": 1189784, "vin": [ { "gen": { "height": 1189774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "706962d1c5de4dc15b05f7ec2ba16c1a5735e2645a60c6b90dd377eaec6b6e5c" } } ], "extra": [ 1, 168, 201, 185, 134, 200, 130, 226, 70, 95, 18, 87, 42, 30, 170, 81, 61, 19, 131, 68, 74, 178, 8, 111, 231, 230, 3, 186, 76, 229, 69, 200, 149, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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