Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd3ecfaf9077c087113823e8ce8a9120c51f878042d5b4314220b1582981cdbd

Tx prefix hash: 478b57bcd68f24a8b0957635a8d2cb2f6b5bc71513df1eb73b0d849fa4ff310f
Tx public key: 83afa3edcc0e08b525d4ea394f49ca204b473c2d134a9697758b6c122065084e
Timestamp: 1699374166 Timestamp [UCT]: 2023-11-07 16:22:46 Age [y:d:h:m:s]: 02:016:08:48:39
Block: 886558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 531487 RingCT/type: yes/0
Extra: 0183afa3edcc0e08b525d4ea394f49ca204b473c2d134a9697758b6c122065084e0211000000014b8f5122000000000000000000

1 output(s) for total of 0.708704714000 dcy

stealth address amount amount idx
00: d5b97c92534a1ed3aa1372ed413fefd78deb308b56eea91eef904e36bc6f3434 0.708704714000 1342385 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": 886568, "vin": [ { "gen": { "height": 886558 } } ], "vout": [ { "amount": 708704714, "target": { "key": "d5b97c92534a1ed3aa1372ed413fefd78deb308b56eea91eef904e36bc6f3434" } } ], "extra": [ 1, 131, 175, 163, 237, 204, 14, 8, 181, 37, 212, 234, 57, 79, 73, 202, 32, 75, 71, 60, 45, 19, 74, 150, 151, 117, 139, 108, 18, 32, 101, 8, 78, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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