Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0638fdb6efc6cbfe2ddf468214a45998f22fe7616f4bf76a2c611e3dfea04e8e

Tx prefix hash: a8e1b292e7d48a2d25e88749ea6a562811ed57bfa0bc42f21562f67109001c76
Tx public key: 6d5c92a5517f5db9b258b4d096977bb19d169233ae5a7abaf0cdbe4885d8cf49
Timestamp: 1717846755 Timestamp [UCT]: 2024-06-08 11:39:15 Age [y:d:h:m:s]: 00:281:04:15:27
Block: 1039703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200950 RingCT/type: yes/0
Extra: 016d5c92a5517f5db9b258b4d096977bb19d169233ae5a7abaf0cdbe4885d8cf4902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fbe03f25e159ef97026c73b3c1e142d88740bddb8936350261063fee2a073c4 0.600000000000 1508356 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": 1039713, "vin": [ { "gen": { "height": 1039703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fbe03f25e159ef97026c73b3c1e142d88740bddb8936350261063fee2a073c4" } } ], "extra": [ 1, 109, 92, 146, 165, 81, 127, 93, 185, 178, 88, 180, 208, 150, 151, 123, 177, 157, 22, 146, 51, 174, 90, 122, 186, 240, 205, 190, 72, 133, 216, 207, 73, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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