Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36d8141432fbd383d7caa3a1bf7c45866e9f58349fa9e7b6501591ff8192ce29

Tx prefix hash: 08d214bd0984a8d393eebb1c4d062280d5adfc13f7e5cbc819da336b52b44267
Tx public key: 52167d610933b71fc933d2adfb8bdfdcf91907c96577a0c412e6fbddb14af429
Timestamp: 1725849571 Timestamp [UCT]: 2024-09-09 02:39:31 Age [y:d:h:m:s]: 00:213:01:42:08
Block: 1106048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152128 RingCT/type: yes/0
Extra: 0152167d610933b71fc933d2adfb8bdfdcf91907c96577a0c412e6fbddb14af429021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 217f12c830ae561240ae316ea5a28a538766a4f324506b16f1ae05c2ccbf4d66 0.600000000000 1583603 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": 1106058, "vin": [ { "gen": { "height": 1106048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "217f12c830ae561240ae316ea5a28a538766a4f324506b16f1ae05c2ccbf4d66" } } ], "extra": [ 1, 82, 22, 125, 97, 9, 51, 183, 31, 201, 51, 210, 173, 251, 139, 223, 220, 249, 25, 7, 201, 101, 119, 160, 196, 18, 230, 251, 221, 177, 74, 244, 41, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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