Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3981bf186022eebdb9105940ce778b641b2286c91dc8dc9ebef12f5dbb2b6853

Tx prefix hash: 79c1484ef104b1de2cdaecf41011afc1432a52a8b8fd80512602c75c0ad98cd7
Tx public key: 3a95dc6a974609340aaaf20040c9c4f7ab65d645921f9512a4ea03166b95b17e
Timestamp: 1672856156 Timestamp [UCT]: 2023-01-04 18:15:56 Age [y:d:h:m:s]: 02:096:04:20:48
Block: 667578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590420 RingCT/type: yes/0
Extra: 013a95dc6a974609340aaaf20040c9c4f7ab65d645921f9512a4ea03166b95b17e02110000000852542ceb000000000000000000

1 output(s) for total of 3.767358262000 dcy

stealth address amount amount idx
00: 7f9441b607266eef73b3e23e933e41d47df461279193fcc7343c5f6e39f16cc9 3.767358262000 1108791 of 0

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": 667588, "vin": [ { "gen": { "height": 667578 } } ], "vout": [ { "amount": 3767358262, "target": { "key": "7f9441b607266eef73b3e23e933e41d47df461279193fcc7343c5f6e39f16cc9" } } ], "extra": [ 1, 58, 149, 220, 106, 151, 70, 9, 52, 10, 170, 242, 0, 64, 201, 196, 247, 171, 101, 214, 69, 146, 31, 149, 18, 164, 234, 3, 22, 107, 149, 177, 126, 2, 17, 0, 0, 0, 8, 82, 84, 44, 235, 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