Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3886efa35f9da300d50a6fb163ad92c72025fd591e155dc7b17cca134258b14

Tx prefix hash: 73f352c00276cdcc421442f0b44ecf53517b6cbdf61279a93cdb42f81f1710d5
Tx public key: f7e3f662c0e47604c5cd6fa42a462d4c87fcb1f7a52b4dd59761274fa2fc341c
Timestamp: 1695348210 Timestamp [UCT]: 2023-09-22 02:03:30 Age [y:d:h:m:s]: 01:249:05:51:15
Block: 853372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439255 RingCT/type: yes/0
Extra: 01f7e3f662c0e47604c5cd6fa42a462d4c87fcb1f7a52b4dd59761274fa2fc341c021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.912902432000 dcy

stealth address amount amount idx
00: 6f331da8fd4f04c59de66447df3861a0996aa4f3e80e53140f5123c5e02bb7a3 0.912902432000 1307274 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": 853382, "vin": [ { "gen": { "height": 853372 } } ], "vout": [ { "amount": 912902432, "target": { "key": "6f331da8fd4f04c59de66447df3861a0996aa4f3e80e53140f5123c5e02bb7a3" } } ], "extra": [ 1, 247, 227, 246, 98, 192, 228, 118, 4, 197, 205, 111, 164, 42, 70, 45, 76, 135, 252, 177, 247, 165, 43, 77, 213, 151, 97, 39, 79, 162, 252, 52, 28, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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