Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d86e1a1238f65420ddf04d065872c8f0df74e5cd24bab0f101f333fd95bf2e8

Tx prefix hash: 5f4ef803694c65438a54e8d3730781230e1f10693cef359ca397278472dc24fa
Tx public key: a3a5f2ed8591d8403b5c2a20bb271e2e2c00a2b0631993322f0ec482ad79b83c
Timestamp: 1722364204 Timestamp [UCT]: 2024-07-30 18:30:04 Age [y:d:h:m:s]: 00:247:04:50:39
Block: 1077154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176575 RingCT/type: yes/0
Extra: 01a3a5f2ed8591d8403b5c2a20bb271e2e2c00a2b0631993322f0ec482ad79b83c02110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61df09e3b34e60efaf7ecec8390fc5f59e799d713a7c3ff395007504376e7c11 0.600000000000 1549699 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": 1077164, "vin": [ { "gen": { "height": 1077154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61df09e3b34e60efaf7ecec8390fc5f59e799d713a7c3ff395007504376e7c11" } } ], "extra": [ 1, 163, 165, 242, 237, 133, 145, 216, 64, 59, 92, 42, 32, 187, 39, 30, 46, 44, 0, 162, 176, 99, 25, 147, 50, 47, 14, 196, 130, 173, 121, 184, 60, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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