Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f4d4e9b1a6e701248bad69334069c405bfdd4447d18809c121600fbc81bc8ae

Tx prefix hash: 47242766e03b67b61508c6f13050f03cf6c6b6d471bbad95a162b7556ef20d18
Tx public key: 761b8733080a25d1884f58d5ed3f648b57f79bc6eb8fa3f1a2956c1ae59c09ac
Timestamp: 1751080106 Timestamp [UCT]: 2025-06-28 03:08:26 Age [y:d:h:m:s]: 00:139:03:01:46
Block: 1314241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97514 RingCT/type: yes/0
Extra: 01761b8733080a25d1884f58d5ed3f648b57f79bc6eb8fa3f1a2956c1ae59c09ac02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ede1e599ad8f04c7d7abbbda85ef429723471ebbeec3851e88316e6c73c6f5ea 0.600000000000 1801886 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": 1314251, "vin": [ { "gen": { "height": 1314241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ede1e599ad8f04c7d7abbbda85ef429723471ebbeec3851e88316e6c73c6f5ea" } } ], "extra": [ 1, 118, 27, 135, 51, 8, 10, 37, 209, 136, 79, 88, 213, 237, 63, 100, 139, 87, 247, 155, 198, 235, 143, 163, 241, 162, 149, 108, 26, 229, 156, 9, 172, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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