Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16382949941b1b477ef7b260328654e42e8ae59ba8fe5eefc5e4cac7e3a4cd7a

Tx prefix hash: b767376e317564603fa04729d25779e5ef11d50fc36b6940821c9e83ce526799
Tx public key: be6f4f6ae1488bbf0959774da8430c4c84cf8834034cf3aa17d5d7ae010450b5
Timestamp: 1710703324 Timestamp [UCT]: 2024-03-17 19:22:04 Age [y:d:h:m:s]: 01:085:03:19:21
Block: 980504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321854 RingCT/type: yes/0
Extra: 01be6f4f6ae1488bbf0959774da8430c4c84cf8834034cf3aa17d5d7ae010450b502110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b0c49a094fc5a059eb17b6391fcdcb1459861e91729d3a4f37799ad09ee342e 0.600000000000 1440573 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": 980514, "vin": [ { "gen": { "height": 980504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b0c49a094fc5a059eb17b6391fcdcb1459861e91729d3a4f37799ad09ee342e" } } ], "extra": [ 1, 190, 111, 79, 106, 225, 72, 139, 191, 9, 89, 119, 77, 168, 67, 12, 76, 132, 207, 136, 52, 3, 76, 243, 170, 23, 213, 215, 174, 1, 4, 80, 181, 2, 17, 0, 0, 0, 10, 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