Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9828f2cbcf4eac9d3cf7de48620aeb2d24743481ad49e46b73a34a14b8b3c8a

Tx prefix hash: 86a23a670ce0619a92c16bcbe74ed364cf76dad8823c688c099d6f5bc8cadf07
Tx public key: f037416e366b0f375dae0d26c5f0bb6549eaddda91c2a6c8677268cc73b24a4a
Timestamp: 1705148837 Timestamp [UCT]: 2024-01-13 12:27:17 Age [y:d:h:m:s]: 01:096:10:53:35
Block: 934419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330052 RingCT/type: yes/0
Extra: 01f037416e366b0f375dae0d26c5f0bb6549eaddda91c2a6c8677268cc73b24a4a0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3810114d5cf2e103e3d536e97f10d4bf71041cfbeb600a2da804a3d69e936f64 0.600000000000 1392427 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": 934429, "vin": [ { "gen": { "height": 934419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3810114d5cf2e103e3d536e97f10d4bf71041cfbeb600a2da804a3d69e936f64" } } ], "extra": [ 1, 240, 55, 65, 110, 54, 107, 15, 55, 93, 174, 13, 38, 197, 240, 187, 101, 73, 234, 221, 218, 145, 194, 166, 200, 103, 114, 104, 204, 115, 178, 74, 74, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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