Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43f05d56b5e8a601a5662e8bfa9e59b059b2b1cad6bdd104c8990bc6d10ffa7d

Tx prefix hash: 4950ab0c170bbc4cdd0ab0d4254a25133f6aad4f7bb7b6ae1042c05dc6f9179a
Tx public key: 72e458796f022b587a8c07c2a7245bac1418a080b83476553e698296e2b69999
Timestamp: 1723806812 Timestamp [UCT]: 2024-08-16 11:13:32 Age [y:d:h:m:s]: 00:250:05:46:00
Block: 1089118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178726 RingCT/type: yes/0
Extra: 0172e458796f022b587a8c07c2a7245bac1418a080b83476553e698296e2b69999021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c051ef6a218dced81420fb6e4d62a5c1cf72c367b6b8372d3f3b65673dc559c2 0.600000000000 1563737 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": 1089128, "vin": [ { "gen": { "height": 1089118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c051ef6a218dced81420fb6e4d62a5c1cf72c367b6b8372d3f3b65673dc559c2" } } ], "extra": [ 1, 114, 228, 88, 121, 111, 2, 43, 88, 122, 140, 7, 194, 167, 36, 91, 172, 20, 24, 160, 128, 184, 52, 118, 85, 62, 105, 130, 150, 226, 182, 153, 153, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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