Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59ee4603151fbc752833358098e9b543e37b6bde872fc9c4714b5c1f02528908

Tx prefix hash: 3c3efec0caca4a83c9aa7cdafd12fc2bdfe6e51431a90ba3511a166a476d27f3
Tx public key: 28e5569def37071d61c886007d06250f55cc7c398638d7f5e2dcb8d0d31bdc2b
Timestamp: 1708037374 Timestamp [UCT]: 2024-02-15 22:49:34 Age [y:d:h:m:s]: 00:332:03:23:58
Block: 958370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237778 RingCT/type: yes/0
Extra: 0128e5569def37071d61c886007d06250f55cc7c398638d7f5e2dcb8d0d31bdc2b0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03bd9d2c32ca62258cd37a8e02b6bbc81d5f7fe110017fd40d8087bb3737210e 0.600000000000 1417729 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": 958380, "vin": [ { "gen": { "height": 958370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03bd9d2c32ca62258cd37a8e02b6bbc81d5f7fe110017fd40d8087bb3737210e" } } ], "extra": [ 1, 40, 229, 86, 157, 239, 55, 7, 29, 97, 200, 134, 0, 125, 6, 37, 15, 85, 204, 124, 57, 134, 56, 215, 245, 226, 220, 184, 208, 211, 27, 220, 43, 2, 17, 0, 0, 0, 4, 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