Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26335ed8fb054b2bb2a0fdcc547aa633782b84351713623e36df7d3d03ac8ebb

Tx prefix hash: 1d256d83f524747c48d71c4f37159c47148bd876b8d9cdda2edfc0ddf18c1be7
Tx public key: 64d67d9d077bdc40d627bf1016ac7fe956b625ea43990d87e1f451bcc9628632
Timestamp: 1723403453 Timestamp [UCT]: 2024-08-11 19:10:53 Age [y:d:h:m:s]: 00:105:04:14:17
Block: 1085762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75250 RingCT/type: yes/0
Extra: 0164d67d9d077bdc40d627bf1016ac7fe956b625ea43990d87e1f451bcc9628632021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f88b8844f3631327bb67cacc2164f664c49ab3aa218a916ade71d5f0a8bed6f 0.600000000000 1560351 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": 1085772, "vin": [ { "gen": { "height": 1085762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f88b8844f3631327bb67cacc2164f664c49ab3aa218a916ade71d5f0a8bed6f" } } ], "extra": [ 1, 100, 214, 125, 157, 7, 123, 220, 64, 214, 39, 191, 16, 22, 172, 127, 233, 86, 182, 37, 234, 67, 153, 13, 135, 225, 244, 81, 188, 201, 98, 134, 50, 2, 17, 0, 0, 0, 1, 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