Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 394d22182d8ce5320d47448cc8c1799a040555a19b5a797b7228bdfa0267e0ae

Tx prefix hash: 356080a77fdc0a84ed49b78ec0165c794036f1050c1a155064a322c69c43732b
Tx public key: 072bd0c5eb48280645995feb33a064e2d9af60e33e0725cf0412240a40df3ec5
Timestamp: 1686388120 Timestamp [UCT]: 2023-06-10 09:08:40 Age [y:d:h:m:s]: 01:281:03:28:01
Block: 779154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462118 RingCT/type: yes/0
Extra: 01072bd0c5eb48280645995feb33a064e2d9af60e33e0725cf0412240a40df3ec502110000000175e3f0e9000000000000000000

1 output(s) for total of 1.608197995000 dcy

stealth address amount amount idx
00: adc87b0af2b7bb56b6bff3df0a6b3ee8e7c260142683c135ff230ba7f617f4be 1.608197995000 1228799 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": 779164, "vin": [ { "gen": { "height": 779154 } } ], "vout": [ { "amount": 1608197995, "target": { "key": "adc87b0af2b7bb56b6bff3df0a6b3ee8e7c260142683c135ff230ba7f617f4be" } } ], "extra": [ 1, 7, 43, 208, 197, 235, 72, 40, 6, 69, 153, 95, 235, 51, 160, 100, 226, 217, 175, 96, 227, 62, 7, 37, 207, 4, 18, 36, 10, 64, 223, 62, 197, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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