Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b31746f7fcdd52fe35ff2e71381d9818349d539cd84a83d974983b7faea894d

Tx prefix hash: fc927534e644b7fed4a623b80cac376ae2525ae910c69a2d659405f1397d9f81
Tx public key: 41405e236981f0c5e71430f7c64865c8f5622b24ac6493fd4504446cff3f57d0
Timestamp: 1744922025 Timestamp [UCT]: 2025-04-17 20:33:45 Age [y:d:h:m:s]: 00:289:15:46:11
Block: 1263651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204666 RingCT/type: yes/0
Extra: 0141405e236981f0c5e71430f7c64865c8f5622b24ac6493fd4504446cff3f57d0021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b938b90fbaf15ba7ce60afb7b273dee5550480429a97d54bfec911a8c52732a4 0.600000000000 1750842 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": 1263661, "vin": [ { "gen": { "height": 1263651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b938b90fbaf15ba7ce60afb7b273dee5550480429a97d54bfec911a8c52732a4" } } ], "extra": [ 1, 65, 64, 94, 35, 105, 129, 240, 197, 231, 20, 48, 247, 198, 72, 101, 200, 245, 98, 43, 36, 172, 100, 147, 253, 69, 4, 68, 108, 255, 63, 87, 208, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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