Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8fa4c2377f0a86539c15beae376b4e43f4b2a55a858842c3b371e2fb50cd98a

Tx prefix hash: 949b22b1c6c4c8fbdeaa335ab03b7e12d729a4c2ca27af6844f072c6a413e757
Tx public key: 00137271dc89fef6a4717c15aec30a932801f559e9240001ae4bb15f509b10de
Timestamp: 1710354926 Timestamp [UCT]: 2024-03-13 18:35:26 Age [y:d:h:m:s]: 00:346:22:40:55
Block: 977610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248031 RingCT/type: yes/0
Extra: 0100137271dc89fef6a4717c15aec30a932801f559e9240001ae4bb15f509b10de02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8db5909864486f3edeb7eae0017589a779d6cb90788a637d86d99e2aaff701af 0.600000000000 1437613 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": 977620, "vin": [ { "gen": { "height": 977610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8db5909864486f3edeb7eae0017589a779d6cb90788a637d86d99e2aaff701af" } } ], "extra": [ 1, 0, 19, 114, 113, 220, 137, 254, 246, 164, 113, 124, 21, 174, 195, 10, 147, 40, 1, 245, 89, 233, 36, 0, 1, 174, 75, 177, 95, 80, 155, 16, 222, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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