Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3facffebcd263ad20307dabbe5a25afc265da220e381747e7c181f3437dc6c8

Tx prefix hash: 127ccdf2b3c7b3395d4b26150f5e95611b85c3015a7604d1d4fae08312335e0d
Tx public key: 8c043e47c4c20ec5faa8dcbe03232a057fc03c0e67bd1a12bf89d8e4fa51622c
Timestamp: 1720162634 Timestamp [UCT]: 2024-07-05 06:57:14 Age [y:d:h:m:s]: 00:142:10:45:44
Block: 1058898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101942 RingCT/type: yes/0
Extra: 018c043e47c4c20ec5faa8dcbe03232a057fc03c0e67bd1a12bf89d8e4fa51622c0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30d16d5f76e25fb12a97e32cd8a4b93688b8c292491a9001991cacc308d3a721 0.600000000000 1529357 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": 1058908, "vin": [ { "gen": { "height": 1058898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30d16d5f76e25fb12a97e32cd8a4b93688b8c292491a9001991cacc308d3a721" } } ], "extra": [ 1, 140, 4, 62, 71, 196, 194, 14, 197, 250, 168, 220, 190, 3, 35, 42, 5, 127, 192, 60, 14, 103, 189, 26, 18, 191, 137, 216, 228, 250, 81, 98, 44, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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