Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7d355c43d45d39f3c1c25f8406ea73fa40defa0a3e41bd795e2915f209ab542

Tx prefix hash: 00730440d86d88d9467c0bb544498cf62a1b2de56bb7918a320eab69262bf01f
Tx public key: 6971514fbfd0c920554aededaba52a6ef39ef50b5bb2a9b95e33f809e3cb61e0
Timestamp: 1682865806 Timestamp [UCT]: 2023-04-30 14:43:26 Age [y:d:h:m:s]: 02:191:15:54:00
Block: 749944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 656806 RingCT/type: yes/0
Extra: 016971514fbfd0c920554aededaba52a6ef39ef50b5bb2a9b95e33f809e3cb61e00211000000027e406890000000000000000000

1 output(s) for total of 2.009668451000 dcy

stealth address amount amount idx
00: d555ed840fa4ce6e03cc62c1fcb4c6d5c874fc1cb2246980b1fac7fe20d5d829 2.009668451000 1197971 of 0

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": 749954, "vin": [ { "gen": { "height": 749944 } } ], "vout": [ { "amount": 2009668451, "target": { "key": "d555ed840fa4ce6e03cc62c1fcb4c6d5c874fc1cb2246980b1fac7fe20d5d829" } } ], "extra": [ 1, 105, 113, 81, 79, 191, 208, 201, 32, 85, 74, 237, 237, 171, 165, 42, 110, 243, 158, 245, 11, 91, 178, 169, 185, 94, 51, 248, 9, 227, 203, 97, 224, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 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