Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1305b0d6e5fca085d0250cdabac8cec758c24edf65d753876cb1ea0788c083c9

Tx prefix hash: f3f41416324d1ea192a484f0855a74ae02c5d10ef67351138ee2e5c5b258b759
Tx public key: 27f82920e11ee5fd5abc023c15e3ac57e9aad0f47f086b1aedd9bad4fb3af5ae
Timestamp: 1709939922 Timestamp [UCT]: 2024-03-08 23:18:42 Age [y:d:h:m:s]: 01:095:15:18:19
Block: 974163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329348 RingCT/type: yes/0
Extra: 0127f82920e11ee5fd5abc023c15e3ac57e9aad0f47f086b1aedd9bad4fb3af5ae02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f6ccf577aaa4c86876c955d539ccdf4bd9e526a118c50742de610fe201a9981 0.600000000000 1434114 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": 974173, "vin": [ { "gen": { "height": 974163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f6ccf577aaa4c86876c955d539ccdf4bd9e526a118c50742de610fe201a9981" } } ], "extra": [ 1, 39, 248, 41, 32, 225, 30, 229, 253, 90, 188, 2, 60, 21, 227, 172, 87, 233, 170, 208, 244, 127, 8, 107, 26, 237, 217, 186, 212, 251, 58, 245, 174, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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