Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 484234a70b1ca2559add8cc9f4e8444b490e1c56bfe4c9868ff5689947c49e39

Tx prefix hash: 373b1ccb2b8920735c17e6c1b63367e4d604f761f6019e7728c1b7b02f433d6e
Tx public key: 098f9da70ce442dcdadda7085a7d054a83cfb75f428e3dbf8469af4068b743d1
Timestamp: 1737154854 Timestamp [UCT]: 2025-01-17 23:00:54 Age [y:d:h:m:s]: 00:058:12:13:42
Block: 1199623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41612 RingCT/type: yes/0
Extra: 01098f9da70ce442dcdadda7085a7d054a83cfb75f428e3dbf8469af4068b743d1021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 682923c1e60cdd2080d8a7ef9735d4f29c0a9e155e6245e0556fab790e76c2fd 0.600000000000 1686256 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": 1199633, "vin": [ { "gen": { "height": 1199623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "682923c1e60cdd2080d8a7ef9735d4f29c0a9e155e6245e0556fab790e76c2fd" } } ], "extra": [ 1, 9, 143, 157, 167, 12, 228, 66, 220, 218, 221, 167, 8, 90, 125, 5, 74, 131, 207, 183, 95, 66, 142, 61, 191, 132, 105, 175, 64, 104, 183, 67, 209, 2, 17, 0, 0, 0, 2, 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