Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b353398bf3cf78287f73c678381f10c9d7ff0db2329bde32c36f8693b54cdf2

Tx prefix hash: edfe1d9a0c13fef12786af669f6c7a74216e24da98150d021e9ed8aa51545c51
Tx public key: a1e883148460c4a6b81e09019bf9d17c0872541a25fbbfcd36e1a11adf56f236
Timestamp: 1737991578 Timestamp [UCT]: 2025-01-27 15:26:18 Age [y:d:h:m:s]: 00:002:15:34:07
Block: 1206317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1875 RingCT/type: yes/0
Extra: 01a1e883148460c4a6b81e09019bf9d17c0872541a25fbbfcd36e1a11adf56f236021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de282535aa9700ec4e3a627218cef5f1ec9c3a10f7e2737f71efeb184a3c8782 0.600000000000 1693020 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": 1206327, "vin": [ { "gen": { "height": 1206317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de282535aa9700ec4e3a627218cef5f1ec9c3a10f7e2737f71efeb184a3c8782" } } ], "extra": [ 1, 161, 232, 131, 20, 132, 96, 196, 166, 184, 30, 9, 1, 155, 249, 209, 124, 8, 114, 84, 26, 37, 251, 191, 205, 54, 225, 161, 26, 223, 86, 242, 54, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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