Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc3b0c101b4dd737d2fd3e8b181d5fd606f82f3bdac1a8dd26767da914f1a23b

Tx prefix hash: 48bb405292c414815d49b8ec081d3badf97113fc0413f82f3632fa4d3402f6e7
Tx public key: f2e14ec206435a60066e9d8449b874fd190101f0a0c6e001eaceb2e58f388df6
Timestamp: 1714734283 Timestamp [UCT]: 2024-05-03 11:04:43 Age [y:d:h:m:s]: 00:266:14:00:40
Block: 1013912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190753 RingCT/type: yes/0
Extra: 01f2e14ec206435a60066e9d8449b874fd190101f0a0c6e001eaceb2e58f388df60211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9606e594d788be4c29697faa5ea137f9c0417b3d42852b21698b448ee012cf4 0.600000000000 1476853 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": 1013922, "vin": [ { "gen": { "height": 1013912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9606e594d788be4c29697faa5ea137f9c0417b3d42852b21698b448ee012cf4" } } ], "extra": [ 1, 242, 225, 78, 194, 6, 67, 90, 96, 6, 110, 157, 132, 73, 184, 116, 253, 25, 1, 1, 240, 160, 198, 224, 1, 234, 206, 178, 229, 143, 56, 141, 246, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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