Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 235df241c1cc3f636d24db1a0ad7271114bee2fb9b88b7d5b81ad774359f79be

Tx prefix hash: c5773f5b28a3d088cbd651c63911c365e1da58b84d8fa71e3e2d9d808e609c1a
Tx public key: b9451a85adec8c4945ac22b6bb7ea1a948b55dafe54733e42dc136246705ab49
Timestamp: 1718488987 Timestamp [UCT]: 2024-06-15 22:03:07 Age [y:d:h:m:s]: 00:313:16:00:22
Block: 1045046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224155 RingCT/type: yes/0
Extra: 01b9451a85adec8c4945ac22b6bb7ea1a948b55dafe54733e42dc136246705ab4902110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d713133fd8f6884d685fb0ce8c867c3b364ec7f71b92d0f326316f1b766774c 0.600000000000 1514515 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": 1045056, "vin": [ { "gen": { "height": 1045046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d713133fd8f6884d685fb0ce8c867c3b364ec7f71b92d0f326316f1b766774c" } } ], "extra": [ 1, 185, 69, 26, 133, 173, 236, 140, 73, 69, 172, 34, 182, 187, 126, 161, 169, 72, 181, 93, 175, 229, 71, 51, 228, 45, 193, 54, 36, 103, 5, 171, 73, 2, 17, 0, 0, 0, 4, 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