Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efde8de97c001d7eabfc9aafced18ee72103f36c90458720beee37f7b265d431

Tx prefix hash: 443bb918cf259ac253828c4ce3205ef16f263f9b0ebe76e8623a3b47d3e3c0db
Tx public key: 57241543cdc4bc053b223c4e12bff2ef6a9a3ea444a522cd1023aac4dbabff93
Timestamp: 1718507514 Timestamp [UCT]: 2024-06-16 03:11:54 Age [y:d:h:m:s]: 00:332:19:56:03
Block: 1045196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237866 RingCT/type: yes/0
Extra: 0157241543cdc4bc053b223c4e12bff2ef6a9a3ea444a522cd1023aac4dbabff9302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65e244dba6ce8f9137a619aa6d73618dd08c88d16025000a5a6eaa77ea991c4e 0.600000000000 1514701 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": 1045206, "vin": [ { "gen": { "height": 1045196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65e244dba6ce8f9137a619aa6d73618dd08c88d16025000a5a6eaa77ea991c4e" } } ], "extra": [ 1, 87, 36, 21, 67, 205, 196, 188, 5, 59, 34, 60, 78, 18, 191, 242, 239, 106, 154, 62, 164, 68, 165, 34, 205, 16, 35, 170, 196, 219, 171, 255, 147, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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