Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34ee4f539f5a1dbf7f79e89d82b54f52fb062548493b178691b7fd1e6e308025

Tx prefix hash: a489027020744c0b0674bc5a64f416448878f44c9ba4b223065066fbfc70a3d4
Tx public key: 417170ad9940737057c62e245f64c624e61cf789be799d0ae7c4dde0d5a11a0a
Timestamp: 1725440498 Timestamp [UCT]: 2024-09-04 09:01:38 Age [y:d:h:m:s]: 00:315:19:32:47
Block: 1102659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224523 RingCT/type: yes/0
Extra: 01417170ad9940737057c62e245f64c624e61cf789be799d0ae7c4dde0d5a11a0a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 018444536550070e249649c5f08d3dd8361df176a50a08b49b1b1b21cb47af0f 0.600000000000 1579182 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": 1102669, "vin": [ { "gen": { "height": 1102659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "018444536550070e249649c5f08d3dd8361df176a50a08b49b1b1b21cb47af0f" } } ], "extra": [ 1, 65, 113, 112, 173, 153, 64, 115, 112, 87, 198, 46, 36, 95, 100, 198, 36, 230, 28, 247, 137, 190, 121, 157, 10, 231, 196, 221, 224, 213, 161, 26, 10, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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