Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c38ad41e12cf901c19aeb0e075f6158bbf4aa8371ec41d1bc1bda244d4069f9

Tx prefix hash: 1a8863328da9785fd496c66d8b9f58142b20544ba251c98fe1a8283c34519a3f
Tx public key: ea9c5646c22e9ddc7a79130af3ccfdeeb60753e908bb4b30c93bfa884d9dffc8
Timestamp: 1731917322 Timestamp [UCT]: 2024-11-18 08:08:42 Age [y:d:h:m:s]: 00:005:22:01:23
Block: 1156263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4229 RingCT/type: yes/0
Extra: 01ea9c5646c22e9ddc7a79130af3ccfdeeb60753e908bb4b30c93bfa884d9dffc8021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b06fca2f1d71781fc71432f0bac9ed34cdea31908c3f387da451305f09cae24d 0.600000000000 1641886 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": 1156273, "vin": [ { "gen": { "height": 1156263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b06fca2f1d71781fc71432f0bac9ed34cdea31908c3f387da451305f09cae24d" } } ], "extra": [ 1, 234, 156, 86, 70, 194, 46, 157, 220, 122, 121, 19, 10, 243, 204, 253, 238, 182, 7, 83, 233, 8, 187, 75, 48, 201, 59, 250, 136, 77, 157, 255, 200, 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