Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa2bf7555b7924aa8109be28b523879ab76307ea5992420625b682324fda8503

Tx prefix hash: 1b5d831282c7d48831fc37f40a0996f7a4d52488bbd68440c6b7427b91fb5012
Tx public key: bf8c4e64943d567009cb34774b21f66e5a3dcde147cfc1efc3c53e667b6ee468
Timestamp: 1703941626 Timestamp [UCT]: 2023-12-30 13:07:06 Age [y:d:h:m:s]: 01:019:16:29:35
Block: 924427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275405 RingCT/type: yes/0
Extra: 01bf8c4e64943d567009cb34774b21f66e5a3dcde147cfc1efc3c53e667b6ee468021100000004ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 851a1d0fb2ddd763badf3480c1dfd5911b46b1df5936aa2059f6d58909d1e357 0.600000000000 1382175 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": 924437, "vin": [ { "gen": { "height": 924427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "851a1d0fb2ddd763badf3480c1dfd5911b46b1df5936aa2059f6d58909d1e357" } } ], "extra": [ 1, 191, 140, 78, 100, 148, 61, 86, 112, 9, 203, 52, 119, 75, 33, 246, 110, 90, 61, 205, 225, 71, 207, 193, 239, 195, 197, 62, 102, 123, 110, 228, 104, 2, 17, 0, 0, 0, 4, 172, 50, 141, 17, 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