Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8317ccba7fc415a08eff9df222772667a8a7a526aafdf6b0c2d1409387b221ce

Tx prefix hash: 8c42bbcca7845fb86631bbdfcba83d1dbbed98de5a0c32085b24440bdc53c98a
Tx public key: 584be5aa4c6d92e13f92d1578e6004050434ad6f164712e2fdd4330b6e9a54aa
Timestamp: 1752914510 Timestamp [UCT]: 2025-07-19 08:41:50 Age [y:d:h:m:s]: 00:116:00:33:23
Block: 1328712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81698 RingCT/type: yes/0
Extra: 01584be5aa4c6d92e13f92d1578e6004050434ad6f164712e2fdd4330b6e9a54aa021100000004a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 817d13c7d91a98a905ffd4d829b887bea3e331563644ed97ee91b2149d35d5b9 0.600000000000 1816475 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": 1328722, "vin": [ { "gen": { "height": 1328712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "817d13c7d91a98a905ffd4d829b887bea3e331563644ed97ee91b2149d35d5b9" } } ], "extra": [ 1, 88, 75, 229, 170, 76, 109, 146, 225, 63, 146, 209, 87, 142, 96, 4, 5, 4, 52, 173, 111, 22, 71, 18, 226, 253, 212, 51, 11, 110, 154, 84, 170, 2, 17, 0, 0, 0, 4, 161, 29, 186, 152, 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