Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8171d870f96aed04763fd68f47daca96641fdfd9caf20f7bbddd6a3418ee7ae7

Tx prefix hash: 112700dd0a543fb7b2abacdddec88445996c626052feb2ca23100369e6f4902d
Tx public key: d35b9d7203fd7412b13e2b1b53b072171f0992525451ad6ba2fbc21f38dccd50
Timestamp: 1736534941 Timestamp [UCT]: 2025-01-10 18:49:01 Age [y:d:h:m:s]: 00:079:23:00:07
Block: 1194498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56918 RingCT/type: yes/0
Extra: 01d35b9d7203fd7412b13e2b1b53b072171f0992525451ad6ba2fbc21f38dccd500211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cc8a173473f4840c27e9971ae373cb088d7128e45ff78e49b4db3fb66f569ea 0.600000000000 1681069 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": 1194508, "vin": [ { "gen": { "height": 1194498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cc8a173473f4840c27e9971ae373cb088d7128e45ff78e49b4db3fb66f569ea" } } ], "extra": [ 1, 211, 91, 157, 114, 3, 253, 116, 18, 177, 62, 43, 27, 83, 176, 114, 23, 31, 9, 146, 82, 84, 81, 173, 107, 162, 251, 194, 31, 56, 220, 205, 80, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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