Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4124b943d260872b5eedbb2e3b4ac685bf1f2bee1ab3e1649747b58edbb42a33

Tx prefix hash: 869dc92c21325b95b9513182ae395e248d3e127d3e66fdc776fe9f8846d9f593
Tx public key: b3cf8a72de418bb039a6a183b5c7e8ff6d035df20462091cae4be588e7ac9889
Timestamp: 1575682129 Timestamp [UCT]: 2019-12-07 01:28:49 Age [y:d:h:m:s]: 04:355:23:12:34
Block: 22387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0967 kB
Tx version: 2 No of confirmations: 1139374 RingCT/type: yes/0
Extra: 01b3cf8a72de418bb039a6a183b5c7e8ff6d035df20462091cae4be588e7ac9889020d3930303100010000000e90824d

1 output(s) for total of 517.396455453000 dcy

stealth address amount amount idx
00: 9e14c3c32527c3caf4cb1c782d39e6721cc2a0e40acdf9815de2632b63691792 517.396455453000 35314 of 0

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": 22397, "vin": [ { "gen": { "height": 22387 } } ], "vout": [ { "amount": 517396455453, "target": { "key": "9e14c3c32527c3caf4cb1c782d39e6721cc2a0e40acdf9815de2632b63691792" } } ], "extra": [ 1, 179, 207, 138, 114, 222, 65, 139, 176, 57, 166, 161, 131, 181, 199, 232, 255, 109, 3, 93, 242, 4, 98, 9, 28, 174, 75, 229, 136, 231, 172, 152, 137, 2, 13, 57, 48, 48, 49, 0, 1, 0, 0, 0, 14, 144, 130, 77 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8