Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 287466da0b8bc265289178540d1150daf33c00ac867041d040efd5e6e0011d6f

Tx prefix hash: d8f00eaa07dcd6d5c68f903bc251f82d5f9bf9427d671128804cf0510c5fc65c
Tx public key: 6e89518ae900271f6bae67db51ac1271744ca244c6000ea29d4d8172fbdd04fd
Timestamp: 1719841786 Timestamp [UCT]: 2024-07-01 13:49:46 Age [y:d:h:m:s]: 00:331:18:46:14
Block: 1056242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237129 RingCT/type: yes/0
Extra: 016e89518ae900271f6bae67db51ac1271744ca244c6000ea29d4d8172fbdd04fd021100000002ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3db3984bbac816e80c7d226f7c1af7ed4b51c8ca21f87fe3691c14f8e3701c7 0.600000000000 1526655 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": 1056252, "vin": [ { "gen": { "height": 1056242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3db3984bbac816e80c7d226f7c1af7ed4b51c8ca21f87fe3691c14f8e3701c7" } } ], "extra": [ 1, 110, 137, 81, 138, 233, 0, 39, 31, 107, 174, 103, 219, 81, 172, 18, 113, 116, 76, 162, 68, 198, 0, 14, 162, 157, 77, 129, 114, 251, 221, 4, 253, 2, 17, 0, 0, 0, 2, 221, 211, 219, 145, 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