Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 084fa0cfca104b7a2fdfbbc3322ffd097d991da5861da1fdba85b8fd05284220

Tx prefix hash: 0b97eb8bf13e6a7f414f50e255880ea2118ba23eb5b7d1049ff63e6cee78e7db
Tx public key: 49b6c9f1ceae89a97a3c93ee25771ef0b44a9e72d4ed800667d838022d922dd8
Timestamp: 1711360908 Timestamp [UCT]: 2024-03-25 10:01:48 Age [y:d:h:m:s]: 00:305:13:52:21
Block: 985961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218660 RingCT/type: yes/0
Extra: 0149b6c9f1ceae89a97a3c93ee25771ef0b44a9e72d4ed800667d838022d922dd802110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 756f01d340547bc37a28ae7792504cae5e6c3994362947ba739c58d68989ae8d 0.600000000000 1446182 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": 985971, "vin": [ { "gen": { "height": 985961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "756f01d340547bc37a28ae7792504cae5e6c3994362947ba739c58d68989ae8d" } } ], "extra": [ 1, 73, 182, 201, 241, 206, 174, 137, 169, 122, 60, 147, 238, 37, 119, 30, 240, 180, 74, 158, 114, 212, 237, 128, 6, 103, 216, 56, 2, 45, 146, 45, 216, 2, 17, 0, 0, 0, 10, 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