Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eefc183abe733a2f94bc348cd6f269da5d79a9c23a68622038ca2401e0e3ea31

Tx prefix hash: 5a4666b13d1088d8d69d7f32753d7f0f2874569cd42257438c4b447e2903ca1b
Tx public key: 69293c3c301d71699f695b21a87ad44cebbd4d68bf9e9f93431a4dfb6070bd61
Timestamp: 1675529916 Timestamp [UCT]: 2023-02-04 16:58:36 Age [y:d:h:m:s]: 02:021:08:25:12
Block: 689765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 536824 RingCT/type: yes/0
Extra: 0169293c3c301d71699f695b21a87ad44cebbd4d68bf9e9f93431a4dfb6070bd610211000000015029cbac000000000000000000

1 output(s) for total of 3.180695894000 dcy

stealth address amount amount idx
00: 0a617795e8b494cc355ba4d8da48c30d16f93112fa69265674d71321a7e74ee2 3.180695894000 1132463 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": 689775, "vin": [ { "gen": { "height": 689765 } } ], "vout": [ { "amount": 3180695894, "target": { "key": "0a617795e8b494cc355ba4d8da48c30d16f93112fa69265674d71321a7e74ee2" } } ], "extra": [ 1, 105, 41, 60, 60, 48, 29, 113, 105, 159, 105, 91, 33, 168, 122, 212, 76, 235, 189, 77, 104, 191, 158, 159, 147, 67, 26, 77, 251, 96, 112, 189, 97, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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