Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 406b76f498efe260f9c6afc31ee306a6919a1f49e016a68b6d65c13b0c92e36b

Tx prefix hash: ee7a329f305e63a5e6cd2ac515eb54dddeb0e9e5f52ea17b68a419b77f86f524
Tx public key: aeeb6170143c4f2aa224fdbc84dbfbed7637f8c253b5ce7577449868eb9e84b9
Timestamp: 1722833590 Timestamp [UCT]: 2024-08-05 04:53:10 Age [y:d:h:m:s]: 00:224:07:20:59
Block: 1081042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160223 RingCT/type: yes/0
Extra: 01aeeb6170143c4f2aa224fdbc84dbfbed7637f8c253b5ce7577449868eb9e84b902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83a6eb0af3bb3430c56901470ae9437390eda85ecda6082688fb60793c020174 0.600000000000 1554635 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": 1081052, "vin": [ { "gen": { "height": 1081042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83a6eb0af3bb3430c56901470ae9437390eda85ecda6082688fb60793c020174" } } ], "extra": [ 1, 174, 235, 97, 112, 20, 60, 79, 42, 162, 36, 253, 188, 132, 219, 251, 237, 118, 55, 248, 194, 83, 181, 206, 117, 119, 68, 152, 104, 235, 158, 132, 185, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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