Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 768b0e986a2c2fab85981da1ee3c898c0c20418eaced9d77254888e3158d8cac

Tx prefix hash: d4fe21cb9d4292d225788b7e6b7a6ee4e0cf8e7117d95eeda21fb656531feac6
Tx public key: 73f51483083c0284a2600c982d2c0cf19dbd1271bc01b3e92df2e63caedfbc98
Timestamp: 1735446536 Timestamp [UCT]: 2024-12-29 04:28:56 Age [y:d:h:m:s]: 00:324:13:04:27
Block: 1185481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229481 RingCT/type: yes/0
Extra: 0173f51483083c0284a2600c982d2c0cf19dbd1271bc01b3e92df2e63caedfbc9802110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51c6961609ff4b065fcedb51587741d526214df80c39ea32d78e7b134b064bbd 0.600000000000 1671952 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": 1185491, "vin": [ { "gen": { "height": 1185481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51c6961609ff4b065fcedb51587741d526214df80c39ea32d78e7b134b064bbd" } } ], "extra": [ 1, 115, 245, 20, 131, 8, 60, 2, 132, 162, 96, 12, 152, 45, 44, 12, 241, 157, 189, 18, 113, 188, 1, 179, 233, 45, 242, 230, 60, 174, 223, 188, 152, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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