Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a66d3686f86634bb7fa9987dcd66b9f763e5f3f23d27fa077ecb6d1e901278cc

Tx prefix hash: a75596894c3412afc369d468b7e7eb26c4da43ae8f76f3d0f12913f5ddd861b7
Tx public key: a9598068da84089af7f765fe9ce7cd10a90eced0aeccc357c526b3bc6496c603
Timestamp: 1728174269 Timestamp [UCT]: 2024-10-06 00:24:29 Age [y:d:h:m:s]: 00:161:08:25:09
Block: 1125326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115119 RingCT/type: yes/0
Extra: 01a9598068da84089af7f765fe9ce7cd10a90eced0aeccc357c526b3bc6496c60302110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5f44069345a8e88ef18cef2ebc1222e5b7e6b80b03c48d1a8215b585e9f77c1 0.600000000000 1608007 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": 1125336, "vin": [ { "gen": { "height": 1125326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5f44069345a8e88ef18cef2ebc1222e5b7e6b80b03c48d1a8215b585e9f77c1" } } ], "extra": [ 1, 169, 89, 128, 104, 218, 132, 8, 154, 247, 247, 101, 254, 156, 231, 205, 16, 169, 14, 206, 208, 174, 204, 195, 87, 197, 38, 179, 188, 100, 150, 198, 3, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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