Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e535372759ddc806434eea97fae31eb39b01f519830f92c9b90434b3904208e

Tx prefix hash: 5383a2b94298777d0b0ed5672111438a06f6c48bf359fa0311c7f7fe87f6dfaa
Tx public key: 35dbcde564dd478f657e4f595df0c360b3e8e9a00b33e5324cc4b6791c6abe8c
Timestamp: 1708051652 Timestamp [UCT]: 2024-02-16 02:47:32 Age [y:d:h:m:s]: 01:113:00:15:02
Block: 958492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341849 RingCT/type: yes/0
Extra: 0135dbcde564dd478f657e4f595df0c360b3e8e9a00b33e5324cc4b6791c6abe8c0211000000036d0f39ce000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 435d9bc0e5c877b3c71afdcfee839832d92aae6ac014fa2dcab73558e09e414a 0.600000000000 1417851 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": 958502, "vin": [ { "gen": { "height": 958492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "435d9bc0e5c877b3c71afdcfee839832d92aae6ac014fa2dcab73558e09e414a" } } ], "extra": [ 1, 53, 219, 205, 229, 100, 221, 71, 143, 101, 126, 79, 89, 93, 240, 195, 96, 179, 232, 233, 160, 11, 51, 229, 50, 76, 196, 182, 121, 28, 106, 190, 140, 2, 17, 0, 0, 0, 3, 109, 15, 57, 206, 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