Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f62bba3eb8cc1b6194b5cf23dcf28d15c2834c1b38c2273c5cb98c0b316d3d82

Tx prefix hash: 874d86501d982530d632495cbb3f407a40e17d2a1ad4c0dde1e27bbda3532406
Tx public key: a1c61fb1a4086de8166a671245e419a234d5f1caeee20291bcdb4beeebb7dfbc
Timestamp: 1713480402 Timestamp [UCT]: 2024-04-18 22:46:42 Age [y:d:h:m:s]: 00:226:11:57:56
Block: 1003493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162163 RingCT/type: yes/0
Extra: 01a1c61fb1a4086de8166a671245e419a234d5f1caeee20291bcdb4beeebb7dfbc021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d66f2fed5bfc4c171b53c9723243930429ebaff917fade479c214d82f750ddd9 0.600000000000 1464035 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": 1003503, "vin": [ { "gen": { "height": 1003493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d66f2fed5bfc4c171b53c9723243930429ebaff917fade479c214d82f750ddd9" } } ], "extra": [ 1, 161, 198, 31, 177, 164, 8, 109, 232, 22, 106, 103, 18, 69, 228, 25, 162, 52, 213, 241, 202, 238, 226, 2, 145, 188, 219, 75, 238, 235, 183, 223, 188, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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