Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e542f4a9a4d73768c4d46075ce16c51ddcb86f4af2d0bd00fa4f8aa588223b2

Tx prefix hash: b508749bfec5955ddfe90d09b01c0ca42205aff7150ed87b715b99a1d941c884
Tx public key: 10573430ad6933e1a0f7cb6108b977f047d611f6852abffc6739d1512f7ec9d3
Timestamp: 1737734826 Timestamp [UCT]: 2025-01-24 16:07:06 Age [y:d:h:m:s]: 00:144:08:39:52
Block: 1204381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102921 RingCT/type: yes/0
Extra: 0110573430ad6933e1a0f7cb6108b977f047d611f6852abffc6739d1512f7ec9d302110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcec2aa779db8e385a0d3365000b39aa9fb82f19fa05a49701d03dc7d825e6b4 0.600000000000 1691066 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": 1204391, "vin": [ { "gen": { "height": 1204381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcec2aa779db8e385a0d3365000b39aa9fb82f19fa05a49701d03dc7d825e6b4" } } ], "extra": [ 1, 16, 87, 52, 48, 173, 105, 51, 225, 160, 247, 203, 97, 8, 185, 119, 240, 71, 214, 17, 246, 133, 42, 191, 252, 103, 57, 209, 81, 47, 126, 201, 211, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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