Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 813f2feaeb35827ce19fc326dc3dbd29c0fc75c54ea78e693b75ea7b2515686d

Tx prefix hash: d038dc7f092602265a8e0cf1d7bcf2251680d7cbf158471f06cc935e6e3cff55
Tx public key: 7bf9231e104fc869630c385161b0ea153ea4b09a5418ef3208d10d706a6db7dd
Timestamp: 1763919502 Timestamp [UCT]: 2025-11-23 17:38:22 Age [y:d:h:m:s]: 00:002:20:54:20
Block: 1418545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2049 RingCT/type: yes/0
Extra: 017bf9231e104fc869630c385161b0ea153ea4b09a5418ef3208d10d706a6db7dd021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85470e6e32443f1259e01a7945845b836eb5216db878da6c5e4f0d938dfb27e3 0.600000000000 1907078 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": 1418555, "vin": [ { "gen": { "height": 1418545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85470e6e32443f1259e01a7945845b836eb5216db878da6c5e4f0d938dfb27e3" } } ], "extra": [ 1, 123, 249, 35, 30, 16, 79, 200, 105, 99, 12, 56, 81, 97, 176, 234, 21, 62, 164, 176, 154, 84, 24, 239, 50, 8, 209, 13, 112, 106, 109, 183, 221, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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