Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be841dc3d82900e07418ff355450848ccf5af29c026fc9e33de9fc659ad138c6

Tx prefix hash: 6e30a72f35c55fbd42cd31ebdc4019db39073fe711266bb51d8377f18a8c8ae7
Tx public key: cf89c6e8953b36a4aa768d926e9b6330abd11141cd025adf2b55cb039d5d912b
Timestamp: 1703040220 Timestamp [UCT]: 2023-12-20 02:43:40 Age [y:d:h:m:s]: 02:003:03:02:34
Block: 916949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521998 RingCT/type: yes/0
Extra: 01cf89c6e8953b36a4aa768d926e9b6330abd11141cd025adf2b55cb039d5d912b021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9cc949f316e408436b60f93c98798850ecbcf1490b3d21ec50c8a211713970a 0.600000000000 1374511 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": 916959, "vin": [ { "gen": { "height": 916949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9cc949f316e408436b60f93c98798850ecbcf1490b3d21ec50c8a211713970a" } } ], "extra": [ 1, 207, 137, 198, 232, 149, 59, 54, 164, 170, 118, 141, 146, 110, 155, 99, 48, 171, 209, 17, 65, 205, 2, 90, 223, 43, 85, 203, 3, 157, 93, 145, 43, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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