Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c95b6a21a4809871bfc3056753483b336147982f156f77a94f445bfad4bbf4b

Tx prefix hash: ac742ec4e277c6f529a5c52c1156ffeaf8e0cc1dd56d65f1f1bf7ef75f843961
Tx public key: e5e70910ae516318f53d0cc98ca768157669733966d8924f7a3261a6d8d5690f
Timestamp: 1725060332 Timestamp [UCT]: 2024-08-30 23:25:32 Age [y:d:h:m:s]: 00:216:02:15:14
Block: 1099506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154287 RingCT/type: yes/0
Extra: 01e5e70910ae516318f53d0cc98ca768157669733966d8924f7a3261a6d8d5690f02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5e50f920cc3f44acb34f13aaa8d3d35d0c8b26baf5bf7b6f7bfbbfcb7e96b9a 0.600000000000 1575469 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": 1099516, "vin": [ { "gen": { "height": 1099506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5e50f920cc3f44acb34f13aaa8d3d35d0c8b26baf5bf7b6f7bfbbfcb7e96b9a" } } ], "extra": [ 1, 229, 231, 9, 16, 174, 81, 99, 24, 245, 61, 12, 201, 140, 167, 104, 21, 118, 105, 115, 57, 102, 216, 146, 79, 122, 50, 97, 166, 216, 213, 105, 15, 2, 17, 0, 0, 0, 4, 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