Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af895c25ed5ee6a2e2cb97a930a001504b120d0f4a241c87cae2cf161eef8412

Tx prefix hash: 756514ccd546dd0be56743a50ce50cb1ec56915bc1bc27274598fcb091a2c5f9
Tx public key: a8397aeaa3e1473bf916daa50068e2775cabaa8ef2436b82227333525c196aa1
Timestamp: 1719345420 Timestamp [UCT]: 2024-06-25 19:57:00 Age [y:d:h:m:s]: 00:324:02:13:30
Block: 1052119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231615 RingCT/type: yes/0
Extra: 01a8397aeaa3e1473bf916daa50068e2775cabaa8ef2436b82227333525c196aa10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bb023f84684e96dc9b8e75def25166bdd508f1401631243df8d4118d77af919 0.600000000000 1522440 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": 1052129, "vin": [ { "gen": { "height": 1052119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bb023f84684e96dc9b8e75def25166bdd508f1401631243df8d4118d77af919" } } ], "extra": [ 1, 168, 57, 122, 234, 163, 225, 71, 59, 249, 22, 218, 165, 0, 104, 226, 119, 92, 171, 170, 142, 242, 67, 107, 130, 34, 115, 51, 82, 92, 25, 106, 161, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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