Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b48138ed4bbcd26bd88321ef8e0f6d9cfd7c6ec20cb268952edb67a1599d5bb

Tx prefix hash: b2b2bda3c9d23140f3f947533041f0c0e1dce70375d79c4c15476dbedb9828bf
Tx public key: 31608f3c6078f110f6390011d8b146809ab2e87f1f3e2071fb69d9e40b089358
Timestamp: 1745664766 Timestamp [UCT]: 2025-04-26 10:52:46 Age [y:d:h:m:s]: 00:015:06:08:32
Block: 1269820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10901 RingCT/type: yes/0
Extra: 0131608f3c6078f110f6390011d8b146809ab2e87f1f3e2071fb69d9e40b08935802110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cd0dd7e6f7219be20163716d45c00bcb132a93011b6d6ad26aa5e4f24e36cf1 0.600000000000 1757059 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": 1269830, "vin": [ { "gen": { "height": 1269820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cd0dd7e6f7219be20163716d45c00bcb132a93011b6d6ad26aa5e4f24e36cf1" } } ], "extra": [ 1, 49, 96, 143, 60, 96, 120, 241, 16, 246, 57, 0, 17, 216, 177, 70, 128, 154, 178, 232, 127, 31, 62, 32, 113, 251, 105, 217, 228, 11, 8, 147, 88, 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