Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31213e23db7060e9d99223969a2faf4ebfb756037ee5c4adcc27d0eb393df18b

Tx prefix hash: fd0d939f7f33c67e4b68fa8ae5ccb273accad9f9fb6274d516e183e041f861d5
Tx public key: ba0fefa3b7805b4bd23f78c454bf89d2a44f8b41cd23a3c2ead4ac0a2ca386ae
Timestamp: 1656976129 Timestamp [UCT]: 2022-07-04 23:08:49 Age [y:d:h:m:s]: 02:330:09:14:24
Block: 536754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 757317 RingCT/type: yes/0
Extra: 01ba0fefa3b7805b4bd23f78c454bf89d2a44f8b41cd23a3c2ead4ac0a2ca386ae0211000000035eb576c5000000000000000000

1 output(s) for total of 10.221422321000 dcy

stealth address amount amount idx
00: 75a71647c38acef7905f3991e5087c068a23eb23a4a9eaf322cc16f5c7e52082 10.221422321000 966553 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": 536764, "vin": [ { "gen": { "height": 536754 } } ], "vout": [ { "amount": 10221422321, "target": { "key": "75a71647c38acef7905f3991e5087c068a23eb23a4a9eaf322cc16f5c7e52082" } } ], "extra": [ 1, 186, 15, 239, 163, 183, 128, 91, 75, 210, 63, 120, 196, 84, 191, 137, 210, 164, 79, 139, 65, 205, 35, 163, 194, 234, 212, 172, 10, 44, 163, 134, 174, 2, 17, 0, 0, 0, 3, 94, 181, 118, 197, 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