Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07eeaf52ac053ba074123d8fb15dd66aa3422f37417b180d8b8d45c4cb540f9b

Tx prefix hash: a984bbd1be6f9af82d4697f77ad0d1849f89ab6b9fdebad03fbc11424f91e1e6
Tx public key: 29d2bd9650211071fcd2c05a23c7f83243d4ad1f9dd339b9108bbb4999158732
Timestamp: 1723171089 Timestamp [UCT]: 2024-08-09 02:38:09 Age [y:d:h:m:s]: 00:241:02:02:55
Block: 1083836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172187 RingCT/type: yes/0
Extra: 0129d2bd9650211071fcd2c05a23c7f83243d4ad1f9dd339b9108bbb499915873202110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 514e6402b4fea5bc686bec6bfc47ea74302e2172b1d52cb43449bbed3b6d9f0f 0.600000000000 1557903 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": 1083846, "vin": [ { "gen": { "height": 1083836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "514e6402b4fea5bc686bec6bfc47ea74302e2172b1d52cb43449bbed3b6d9f0f" } } ], "extra": [ 1, 41, 210, 189, 150, 80, 33, 16, 113, 252, 210, 192, 90, 35, 199, 248, 50, 67, 212, 173, 31, 157, 211, 57, 185, 16, 139, 187, 73, 153, 21, 135, 50, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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